Added the catch of wrong content-type returning meaningful message #714
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Added test for the above use case Signed-off-by: Paolo Patierno <ppatierno@live.com>
scholzj
approved these changes
Nov 24, 2022
Signed-off-by: Paolo Patierno <ppatierno@live.com>
im-konge
approved these changes
Nov 24, 2022
|
Travis seems to have problem setting up environment for s390 architecture. Going to merge this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes #598
The bridge is now handling requests on sending messages which come with a bad content-type and returning a more meaningful error like the following:
{ "error_code":400, "message":"[Bad Request] Cannot find body processor for content type application/x-www-form-urlencoded" }